Skip to main content
Version: 5.1.0.0

Description

The activity response is a special activity. Actually it is an activity, which calls channels, but response calls inbound channels. Some of the Inbound channels, e.g. File Listener or HTTP GET Receiver, see in channel for more information, needs some message to stop the connection between Orchestra and the other system.

Purpose of object​

In some cases a "send" to an inbound channel could be necessary.

Create

  1. Create a process model

  2. Then point the mouse on "process", as default, this window is on the right side of the Orchestra window.

  3. Click on the folder activities to see its content.

  4. Click on "Response".

  5. Click on any place in your process model.

  6. Integrate it in process schedule, by clicking on the response icon and drag and drop the arrow to the to be connected item.

  7. Connect it with Inbound channel, see in channel for more information, by clicking on the response icon and drag and drop the arrow to the intended channel. A dashed arrow should appear.

Icon​

response_icon.png

Configuration

Label and Non functional properties​

See at common configurations for activities.

Parameter assignment​

In this section you define the parameter, which should be delivered to the channel. Similar to a function call with parameters, may the channel also need some parameters:

process_model_variable_assignment.png

In mapping window can you see the intended parameters to communicate with the inbound channel. The parameters depend on the channels configurations. Most of the channels expects a Orchestra message, which is preallocated with the current message(CURMSG) of process model.

A parameter has following values:

  • Target: The variable name of the parameter in target.

  • Lang: The language of the expression. This can be either Java, XPath or -in case of Native JSON messages-JsonPath, see more information in Glossary.

  • ExpressionShape: The variable, function or value, which will be assigned to target variable. To have an overview of possible values right-click on expression field, to see a choice of possible content. You can insert:

  • A variable from source, e.g. CURMSG or MSG

    process_model_parameter_curmsg.png

    • A value, e.g. string, integer or Boolean

      process_model_parameter_string.png

    • A value generated out of a java function:

      • A Boolean value, whether mass data option is selected for current message

        process_model_parameter_function1.png

      • String value, which includes the name of scenario.

        process_model_parameter_function2.png

      • See a selection of the Orchestra generated Java functions for more information.

    • A value generated out of XPATH expression using the XPath Editor.

    • A value generated out of Environment entry expression using the Environment Entry builder.

If you choose one single record you can see additional information in fields target and State.

Target gives information about the target type: variable name <data type>, short description of intended value
In field state you can see problems and mismatches. In case of a error the text contains the error message. If everything is alright it just says "OK".

The button Automapping automatically clears wrong connection and maps values with same name.
Button Clear errors refreshes the view of parameter. It could be possible that some target values have been changed. With clear errors reloads Orchestra the parameters to actual state.

In field namespace context you can add or remove namespaces for Xpath expressions. This is commonly used and filled automatically, if you declare a XPath. The namespace URI of the selected record gets a prefix for potential later use.